Single-Party, Secured Multi-Channel Authentication

ABSTRACT

A method for using multiple channels to authenticate a user, wherein a first authentication parameter from a first device associated with a user is received over a first channel, a token value is transmitted to the user on the first channel, and the user transmits the token value and a second authentication parameter over a second channel. The token value is used to associate the first authentication parameter to the second authentication parameter, whereby the user is authenticated on the first channel.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of U.S. PatentApplication No. 60/849,971, filed on Oct. 6, 2006, entitled “SecureMulti-Channel Authentication,” the disclosure of which is herebyincorporated by reference.

FIELD OF THE INVENTION

The present invention relates generally to using multiple channelsduring the authentication of a single user or multiple users.

BACKGROUND

Electronic commerce depends upon the secure and correct authenticationof the end user. The advent of widespread, successful attacks on simpleuser credentials (user id and password) compromises the ability of usersto perform electronic transactions. Attacks expose users to significantrisk of financial loss, identity theft and/or other inconvenience.Attacks such as desktop viruses, key loggers, man-in-the-middleenvironments, phishing, and pharming all conspire to compromise a user'sidentity, often without the user becoming aware of the problem.

The threat of attacks contributes to an increased service provider costof doing business. Service providers must expend resources to defendagainst attacks, to compensate attacked users, and to reassure usersthat electronic commerce remains safe. Ultimately, the failure toprovide mechanisms that allow users to successfully and securelyauthenticate will erode user confidence in electronic transactions andwill threaten the electronic channels as a viable means of commerce.

Authentication via electronic channels frequently involves thepresentation of both identity data and shared secret data. The sharedsecret data, known only to the user and the service provider,establishes the user identity with a degree of confidence. This form ofauthentication is vulnerable to attack by interception. If the attackeracquires both the identity data and the shared secret, the attacker thenbecomes indistinguishable from the legitimate party in the view of theservice provider. Attackers intercept exchanged data by compromising anendpoint of the electronic channel.

Many service providers enhance this basic data exchange by incorporatinga mechanism that changes the secret data over time in an unpredictablefashion. Thus even the capture of the secret only compromises the useruntil the next change. Unfortunately, mechanisms that change the secretincrease service provider costs and potentially inconvenience the user.For instance, the user may forget whatever device provides the changingsecret. In this case the service provider must provide not only thetime-change augmented authentication, but also an alternativeauthentication process that allows the user to bypass time-changeauthentication if the user forgets the device. This may requireadditional authentication steps by the user or impose restrictions onuser access.

SUMMARY

In one approach, multiple channels may be used to authenticate a user.In one aspect, this includes a method that includes receiving a firstauthentication parameter from a first device associated with a user overa first channel, wherein the user is unauthenticated. The method alsoincludes transmitting a token value and receiving the token value and asecond authentication parameter from a second device over a secondchannel, wherein the second device is associated with the user; andusing the token value to associate the first authentication parameter tothe second authentication parameter.

In another approach, there is a method to access a resource over a firstchannel where the resource requires a second authentication parameterover a second channel. In one aspect of this approach there is a methodincluding receiving a request over a first channel for a resource thatrequires a second authentication parameter; transmitting a token valueover the first channel; receiving the token value and the secondauthentication parameter over a second channel; and using the tokenvalue to associate the request received over the first channel with thesecond authentication parameter received over the second channel.

In another approach, multiple channels may be used to provide a resourceto a first party wherein the access to the resource requires anindication of approval from a second user. In one aspect there is amethod that includes receiving a first authentication parameter from afirst device, wherein the first device is associated with a first user,receiving a request for a resource from the first user that requires anindication of approval of a second user, and transmitting a token valueto the first device. The method also includes receiving a secondauthentication parameter and the token value from a second device,wherein the second device is associated with the second user, using thetoken value to associate the first authentication parameter with thesecond authentication parameter, and receiving an indication of approvalfrom the second user to allow the request from the first user.

In another aspect, the method includes authenticating a first user on afirst channel, receiving a request for a resource from a first deviceover a first channel that requires an indication of approval from asecond user, wherein the first device is associated with a first user,and transmitting a token value to the first device. The method alsoincludes authenticating a second user on a second channel, receiving thetoken value from a second device over the second channel, wherein thesecond device is associated with the second user, and receiving theindication of approval from the second device. The method also includesusing the token value to associate the request from the first devicewith the indication of approval from the second device and providing theresource to the first device.

In another aspect, the method includes authenticating a second user,receiving a token value, wherein the token value is associated with auser session wherein a first user has access to a resource based on anindication of approval from the second user, transmitting informationabout the user session to the device, and receiving instruction from thedevice regarding access of the first user to the resource.

The above mentioned aspects can include one or more of the followingfeatures. The user can be authenticated based on the firstauthentication parameter and the second authentication parameter. Thefirst authentication parameter can be a user ID, password, hard token,soft token, wireless applet, voiceprint, or any combination thereof. Thesecond authentication parameter can be a user ID, a password, a hardtoken, a soft token, a wireless applet, a voiceprint, or any combinationthereof. The first authentication parameter and the secondauthentication parameter can be channel specific. The user can benotified over the second channel that the authentication is complete,allowing the user to continue a user session on the first channel. Thefirst channel can be a phone line, a wireless connection or an onlineconnection and the second channel can be a phone line, a wirelessconnection, or an online connection.

The aspects mentioned above can also include receiving the token valueand at least one additional authentication parameter over at least oneadditional channel. The additional authentication parameter can be auser ID, a password, a partial password, a portion of the firstauthentication parameter, a portion of the second authenticationparameter, a combination of the first and the second authenticationparameters, a hard token, a soft token, a wireless applet, a voiceprint,or any combination thereof. The additional channel may not be the firstor second channel, and the token value can be used to associate thefirst authentication parameter, the second authentication parameter, andthe at least one additional authentication parameter. And the firstauthentication parameter, the second authentication parameter, and theat least one additional authentication parameter can be used toauthenticate the user.

Any of the above aspects can include one or more of the followingfeatures. The resource can require a second authentication parameter andat least one additional authentication parameter. The method can alsoinclude receiving the token value and an additional authenticationparameter over an additional channel, and using the token value toassociate the request received over the first channel with theadditional authentication parameter received over the additionalchannel.

Any of the above aspects can include one or more of the followingfeatures. The resource is provided over the first channel. The methodcan also include receiving a request over the first channel for aresource that requires an additional authentication parameter, receivingthe token value and the additional authentication parameter over anadditional channel, using the token value to associate the requestreceived over the first channel with the additional authenticationparameter received over the additional channel. The additionalauthentication parameter may not be the first authentication parameteror the second authentication parameter in some aspects. The additionalauthentication parameter can require more than either the firstauthentication parameter or the second authentication parameter in anadditional or alternative aspect. And the additional authenticationparameter can be a user ID, password, partial-password, hard token, softtoken, wireless applet, voiceprint, or any combination thereof in someother aspects.

Any of the above aspects above may also include one or more of thefollowing features. At least one additional user provides a token valueover at least one additional channel. The additional user may beauthenticated using a single channel or multi-channel authenticationprior to providing the token value. The at least one additional user mayprovide an indication of approval for a first user to receive arequested resource over a first channel, an authentication parameter, atoken value, or any combination over the at least one additionalchannel.

Any of the aspects above may also include one or more of the followingfeatures. The resource can be provided over the first channel and thesecond channel simultaneously. The first channel can be a phone line, awireless connection, or an online connection and the second channel is aphone line, a wireless connection, or an online connection.

Any of the aspects above may include one or more of the followingfeatures. A user may be authenticated using a multi-channelauthentication process or a single-channel authentication process. Amethod can also include authenticating a user by receiving a firstauthentication parameter from a first device through a first channel.The first device can be associated with the user. Furthermore, theaspects may include one or more of the following features. The firstauthentication parameter can be a user ID, password, hard token, softtoken, wireless applet, voiceprint, or any combination thereof. Thesecond authentication parameter can be a user ID, password, hard token,soft token, wireless applet, voiceprint, or any combination thereof. Thesecond authentication parameter may not be the first authenticationparameter. The second authentication parameter can require more than thefirst authentication parameter. And the first authentication and thesecond authentication parameter can be channel specific.

Any of the aspects above may also include one or more of the followingfeatures. A credential is generated wherein the information associatedwith the credential can indicate that the resource may be provided to afirst device without the second authentication parameter being providedover the second channel. The credential can be a permanent credential, atime-sensitive credential, a credential that expires after a pre-setnumber of user sessions, or any combination thereof. Other features insome aspects may include when the user has exited their initial sessionand is attempting to begin a new session authenticating the user. Themethod can also include receiving a request for the resource from thefirst device over a first channel. The resource can require the secondauthentication parameter provided over the second channel. The methodcan also include processing information associated with a credential;and providing the resource if the information associated with thecredential indicates that the resource should be provided to the firstdevice without the second authentication parameter being provided overthe second channel.

Any of the above aspects can include one or more of the followingfeatures. A first authentication parameter can be received from a firstdevice. The method can also include receiving a first authenticationparameter from a first device over a first channel, receiving a secondauthentication parameter and the token value from a second device,receiving a first authentication parameter from a first device over afirst channel, using the token value to associate the request receivedfrom the first device with the indication of approval from the seconduser received over the second channel, and providing the resource to thefirst device.

Any of the above aspects can include one or more of the followingfeatures. The first authentication parameter can be a user ID, adescriptive title, password, hard token, soft token, wireless applet,voiceprint, or any combination thereof. The first authenticationparameter can be associated with the second user. And the secondauthentication parameter can be a user ID, a descriptive title,password, hard token, soft token, wireless applet, voiceprint, or anycombination thereof.

Any of the above aspects can include one or more of the followingfeatures. A user can be authenticated using a single-channel process ora multi-channel process. The method can also include receiving a user IDand first password associated with a first user over a first channel,authenticating the first user based on the user ID and the firstpassword, receiving a user ID and second password associated with asecond user over a second channel, and authenticating the second userbased on the user ID and second password.

Any of the above aspects can include one or more of the followingfeatures. A credential can be generated with information that indicateswhether a resource may be provided to the first device without theindication of approval from the second user. The credential can be acookie, a permanent credential, a time-sensitive credential, acredential that expires after a pre-set number of user sessions, or anycombination thereof. Other features that may be included in one or moreof the aspects above include when the first user has exited an initialsession and is attempting to begin a new session. The method can alsoinclude authenticating the first user. The method can also includereceiving the first authentication parameter from the first device. Thefirst device can be associated with the first user. The method can alsoinclude receiving a request for the resource from the first device,wherein access to the resource requires an indication of approval fromthe second user, and processing information associated with thecredential. An additional feature that may be included in one or more ofthe aspects above includes providing the resource if the informationassociated with the credential indicates that the resource should beprovided to the first device without the approval of the second user.

Any of the above aspects can include one or more of the followingfeatures. An authentication parameter can be received from a device. Theauthentication parameter can be associated with the second user. Themethod can also include receiving instructions from the second user toterminate the access of the first user to the resource, and receivinginstructions from the second user to limit the access of the first userto the resource. And the second user can limit the access of the firstuser according to a time deadline, or a pre-set number of user sessions.

Any of the above aspects can include one or more of the followingfeatures. A first authentication parameter can be a user ID, adescriptive title, password, hard token, soft token, wireless applet,voiceprint, or any combination thereof. The first authenticationparameter can be associated with a second user or a first user. Thesecond authentication parameter can be a user ID, a descriptive title,password, hard token, soft token, wireless applet, voiceprint, or anycombination thereof. The second authentication parameter can beassociated with the first user or the second user. The secondauthentication parameter may not be the first authentication parameter.The second authentication parameter can require more than the firstauthentication parameter. And the first authentication, the secondauthentication parameter, and the additional authentication parametercan be channel specific. The additional authentication parameter may notbe the first authentication parameter or the second authenticationparameter. The additional authentication parameter can require more thaneither the first authentication parameter or the second authenticationparameter. And the additional authentication parameter can be a user ID,a password, a partial password, a portion of the first authenticationparameter, a portion of the second authentication parameter, acombination of the first and the second authentication parameters, ahard token, a soft token, a wireless applet, a voiceprint, or anycombination thereof.

In another aspect, there is a computer program product for generatingcode on a network. The computer program product is tangibly embodied inan information carrier. The computer program product includesinstructions being operable to cause a data processing apparatus toperform any of the methods described above.

In another aspect, there is a system for generating code on a network.The system includes a computing device. The computing device isconfigured to perform any of the methods described above.

Any of the above described methods and/or apparatuses can include one ormore of the following advantages. An advantage of the disclosedtechnique is that the user does not provide all of their authenticationparameters over a single channel. If an outside party was able tointercept the user's session, they would not be able to access thesession at a later time because the outside party would not have accessto, for example, the user's user ID and password. In addition, if thethird-party was able to access the user ID and password, they would notbe able to complete a transaction or access a resource that required theadditional authentication parameter. Another advantage of the disclosedtechnique is that, for example, the second user's user ID, or otherfirst authentication parameter in alternative embodiments, may beexposed but not the second user's Password, or second authenticationparameter. The first user is then able to access the second user, orregistered user's account information with limited exposure of thesecond user's authentication parameters. Another advantage is that thetechnique can be modified to authenticate or authorize a single user ora group of ‘N’ users. Additionally, the users who are authenticated orauthorized do not need to have a preexisting relationship with theresource provider or provider of the back-end system.

Other aspects and advantages of the present invention will becomeapparent from the following detailed description, taken in conjunctionwith the accompanying drawings, illustrating the principles of theinvention by way of example only.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of the presentinvention, as well as the invention itself, will be more fullyunderstood from the following description of various embodiments, whenread together with the accompanying drawings.

FIG. 1 shows the elements of a multi-channel authentication process.

FIGS. 2A-2C show a single, party, multi-channel authentication process.

FIGS. 3A-3C show a higher level authentication process to access arestricted resource for an single party, over multiple channels.

FIGS. 4A-4C show higher level authentication process to access arestricted resource for an single party, over multiple channels whereina device is also registered as secure for future sessions.

FIGS. 5A-5C show an authentication process used by multiple parties overmultiple channels.

FIG. 6 shows the process whereby a registered user terminates the accessof a first user to a requested resource.

FIGS. 8A-8C show implementations whereby a parent or second jointaccount owner must authorize the session of a minor or first jointaccount owner.

FIG. 8A-8C shows a multi-channel authentication process for a creditcard transaction.

Variations, modifications, and other implementations of what isdescribed herein will occur to those of ordinary skill in the artwithout departing from the spirit and the scope of the invention.Accordingly, the invention is to be not limited by the followingillustrative descriptions.

DETAILED DESCRIPTION

The techniques described herein allow a single user to use at least twodifferent channels sequentially to perform authentication to a singlesession. By using multiple channels, the user is prevented fromproviding all of their authenticating, or personally identifying,information over a single data stream channel that may be intercepted.In addition, if one data stream is intercepted by a third-party tryingto improperly access the user's personal information, the third-partywill be unable to use any intercepted information to later access theuser's account or personal information because the third-party will nothave access to all of the user's authenticating information, only theauthenticating information that was passed over the intercepted channelor data stream. Therefore, access to the user's account or personalinformation is protected.

One implementation of these techniques includes a single user who usesmultiple channels to authenticate their usage. Multiple users can alsouse a multi-channel authentication/authorization technique.

FIG. 1 depicts a system that can be used in some implementations. Thissystem can include, for example, a user agent 1 101, a first channel 5,a user agent 2 102, a second channel 6, at least one additional useragent 103, at least one additional channel 7 and a back end system 100.The back end system 100 is in communication with the different channels5, 6, 7, using interfaces and/or networks associated with each channel(not shown). The user(s) can provide a first authentication parameterover a first channel 5. The back end system 100 includes a tokengenerator module 100 a that generates a token value, and transmits thattoken value to the user over the first channel 5. The user takes thetoken value and uses a second channel where they enter the token valueand a second authentication parameter. This process of entering thetoken value and an additional authentication parameter can be repeatedon an unlimited number of different channels. The back-end system 100includes an authentication module 100 b that uses the token value toassociate the request for a resource or authentication on the firstchannel 5 with the authentication parameters or authorization providedover the second channel 6 and/or additional channels 7. In someembodiments the back-end system 100 can be a single device and in otherembodiments, the back-end system 100 can include multiple devices. Themodules 100 a and 100 b can likewise be part of the same device ordistributed on different devices. In some implementations the user maychoose a different second, or additional channel each time they completethe second part of the authentication process. In some implementations,the user should choose a first and second channel to ensure that all ofthe data being transmitted does not pass over the same data stream. Thisensures that if one channel is intercepted by an unauthorizedthird-party, all of the personal or authentication parameters of theuser is not at risk.

The user agents 101, 102, 103 can be computers, telephones, IP phones,mobile devices (e.g., cellular phones, personal digital assistant (PDA)devices, laptop computers, and/or the like), and/or other communicationdevices.

User agent 1 101 can be associated with a first user or a first device.In some implementations user agent 1 101 can include a first device, andin some other implementations user agent 1 101 can be both the firstchannel 5 and a first device. Similarly, user agent 2 102 can beassociated with a second user or a second device. In someimplementations user agent 2 102 can be a second device, and in someother implementations user agent 2 102 can include both the secondchannel 6 and a second device.

The information entered by the user on the first channel 5 and theinformation entered on the second 6, or additional 7, channels, isassociated by a token. A benefit of the token value is that it allowseasy association of the user's authentication parameters that areentered over multiple channels.

In some implementations user agent 1 101, user agent 2 102 and anyadditional user agent 103 is associated with a single user. In someimplementations each user agent is associated with a different user.

In some implementations, the token value is used when authenticating auser or multiple users over multiple channels. In a first implementationthe token value may ensure that only the device and user areauthenticated, and that other unauthorized users associated with otherdevices do not have access to a user's information or transactionalauthority. A token value can also be mapped back to a database recordand one or more users in some implementations. A token value canassociate the first authentication parameter which is associated withthe first channel, and the second authentication parameter which isassociated with the second channel. The token value can also be used toassociate the Nth parameter with any of the previously entered N-1parameters. In some implementations the token value can associate therequest received over a first channel with an indication ofauthorization from an authenticated user received over a second or Nth(additional) channel. And in some implementations the token will beentered with authenticating data or parameters, not alone or solely withan indication of approval.

In some implementations, the user may determine the relative securitystrength of the token, and in some implementations the resource providermay determine the strength of the token. In some implementations thetoken value can be, for example, a randomly generated alphanumericstring, encrypted, previously known by the account owner or registereduser, unique to the requested resource or authentication level, moresecure depending on the requested resource or authentication level, orany combination thereof. In some implementations the token value can belimited by the number of transactions, a time limit, or be sessionspecific. And in some embodiments, the token may be unique to the eventor scenario.

Information transfer over the first channel 5, second channel 6, and/orat least one additional channel 7 can be based on one or morecommunication protocols and/or communication modes. Communicationprotocols can include, for example, Internet Protocol (IP), Voice overIP (VOIP), Peer-to-Peer (P2P), Hypertext Transfer Protocol (HTTP),Session Initiation Protocol (SIP), Really Simple Syndication (RSS),podcasting, Signaling System #7 (SS7), Global System for MobileCommunications (GSM), Push-to-Talk (PTT), PTT over Cellular (POC),and/or other communication protocols. Communication modes can range fromtextual modality (e.g., electronic mail and/or instant messaging) tographical modality (e.g., still and/or moving pictures) to audiomodality (e.g., voice calls), or any combination thereof.

The first channel 5, the second channel 6, and/or the at least oneadditional channels 7 can include one or more packet-based networksand/or one or more circuit-based networks in any configuration.Packet-based networks can include, for example, the Internet, a carrierInternet Protocol (IP) network (LAN, WAN, or the like), a private IPnetwork, an IP private branch exchange (IPBX), a wireless network (e.g.,a Radio Access Network (RAN)), and/or other packet-based networks.Circuit-based networks can include, for example, the Public SwitchedTelephone Network (PSTN), a legacy private branch exchange (PBX), awireless network (e.g., a RAN), and/or other circuit-based networks.

The first channel 5, second channel 6, and additional channel 7 can beconnected, directly or indirectly to the back-end system 100. Theback-end system 100 can include, for example, an authentication server,an authentication validator, an ID system, a session database, awireless gateway server, a low-value resource validator, a high valueresource validator, a resource validator, a Tellme application, a voiceauthentication validator, and a VRU gateway.

FIG. 2A illustrates a first implementation wherein the user obtains atoken. The technique in FIG. 2A uses a system of several devices toperform the process. This system includes a first channel 101 (includedas part of user agent 1 101), an authentication server 202, anauthentication validator 204, an ID system 206 and a session database208. The first channel 101 can be, for example, a website, a telephoneline, and the like. In FIG. 2A, the user uses the first channel 101 toenter (13) their user ID. Further processing that is illustrated in FIG.2A is completed using the system elements as indicated. A token value isreturned (22) to the first channel 101. In some embodiments a tokenvalue may be an alphanumeric string. In some embodiments the token valueis a single use token. In addition, or alternatively, the token valuemay be time sensitive or valid for a limited duration.

In FIG. 2A, the user using user agent 1 101, associated with the firstchannel requests a log-in challenge (10) from the Authentication Service202. The Authentication Service (AS) 202 clears (11) any current userauthentication credentials and presents the login challenge page 12 onuser agent 1 101. The user provides (13) the user ID, or firstauthentication parameter, to the Authentication Service 202. In someimplementations, the first authentication parameter can be a user ID,password, hard token, soft token, wireless applet, voiceprint, or anycombination of these. In some implementations, the first authenticationparameter can also be specific to the device or type of channel used. Inother words, in some implementations, the user may have a firstauthentication parameter that is specific to a land-line phone, orcellular phone, a computer, or a wireless device.

In some implementations, the authentication validator 204 using (14) theuser ID presented and the authentication context determines that theuser is a valid user (15). The authentication service 202 uses (16) theID system 206 to map the user ID to its global ID 17. Next, theauthentication service 202 transmits a request (18) to the session DB208 to create a record that includes, for example, user ID, global ID,authentication context (including channel) and session ID. The sessionDB 208 creates a token value (19), and combines the token value with thevalues provided and the current time. The session DB 208 also creates asession database entry, setting its authentication status value to:In-Progress (19). The session DB 208 returns all of this information(20) to the authentication service 202 which uses the returned tokenvalue and time 20 to produce an authentication credential. Thisauthentication credential indicates that the user is not yetauthenticated, and includes the global ID, the session ID, the tokenvalue and the time 21. The authentication service 202 sets theauthentication credential to user agent 1 101, and presents (22) thetoken value and instructions to complete authentication on anotherchannel.

The exemplary process of FIG. 2B1 shows the use of user agent 2 102,which can be, for example, a land-line phone. The exemplary process ofFIG. 2B2 shows the use of user agent 2 102, which may be, for example, awireless device. The process of providing the token value and the PIN orpassword, or second authentication parameter, in a second part of theauthentication process will depend on whether the user is attempting toconnect by phone (e.g., FIG. 2B1) or handheld wireless Applet (e.g.,FIG. 2B2). In some implementations, the user enters (27) the token valueprovided and later enters (29) their user password. In otherimplementations, the user can enter the token value and their passwordin a single step. The token value associates the information provided onuser agent 1 101 with the information provided via user agent 2 102.This allows the provided user identification information to beaggregated and used to complete the authentication of the user.

In FIG. 2B1, the second authentication parameter is provided throughuser agent 2 102. In some implementations user agent 2 102 is associatedwith a second channel, in some implementations user agent 2 102 isassociated with both a second channel and a second device. In oneimplementation, FIG. 2B1, when the user requests a connection (25) tothe second channel 102 by telephone, the user dials the telephone numberprovided over the first channel. In some embodiments, the user may diala telephone number that is already known, or was provided to the userbefore the instant session. A VRU Gateway 200 requests the token value(26). After receiving the token value 27, the VRU Gateway 200 requests(28) a PIN, password, or other second authentication parameter from theuser. In some implementations, the second authentication parameter maybe is a user ID, password, hard token, soft token, wireless applet,voiceprint, or any combination, instead of, or in addition to, apassword or PIN.

In FIG. 2B2, the user uses a wireless hand held device to access asecond, or additional, channel. In the wireless handheld embodiment, theuser may be asked to input (127) the token value and the PIN or passwordin a single request. The user will then follow the process of using awireless device as the second device. In some of the embodiments, afterthe token and Password are inputted, any subsequent process is identicalregardless of whether the user is utilizing the phone or a wirelesshand-held device as the second device associated with a second oradditional channel.

In FIGS. 2B1 and 2B2, the Authentication Service 202 requests (30) thesession data from the session DB 208, based on the inputted token value.The session DB 208 uses (31) the token value to acquire and return theentry creation time, user ID, global ID, authentication context(including the original channel), session ID, and authentication status(e.g., In Progress) to the AS 202. The AS 202 validates (32) the sessionentry token, time and authentication status. It obtains (33) the userID, and requests (34) that the authentication validator 204authenticates the user ID, PIN, and authentication context. In someimplementations the PIN is a channel specific PIN (see e.g., FIG. 2B2).On successful authentication (35), the AS 202 sends an indication to thesession DB 208 to update the authentication status (36) in the sessiondatabase entry to, for example, Session Authenticated 37. In someimplementations the session DB 208 may set (85) the authenticationstatus to authentication upgrade. The session database 208 reports back(38) to the AS 202 when the authentication status has been updated. Theuser is informed that authentication was successful and that they cannow continue their session on the user agent 1 101.

In FIG. 2C, the user returns to the first channel and requests (40)authentication completion with the authentication credential. TheAuthentication Service 202 obtains (41) the token value, the global ID,and the time from the authentication credential delivered with the userrequest. The AS 202 requests (30) that the session DB 208 acquire thesession database record associated with the token value provided. Thesession DB 208 returns 931) the session database record that includes,for example, the user ID, global ID, authentication context, tokenvalue, session ID, creation time and authentication status.

The Authentication Service 202 validates (42) the time, authenticationstatus and global ID and transmits (43) the updated authenticationstatus to the session DB 208 which updates (44) the authenticationstatus in the session database 208 to authentication upgrade complete.The session DB 208 then transmits (45) the updated status back to the AS202. The fall authentication credentials 46 are built and returned (47)to user agent 1 101. The user is notified that the authentication iscomplete and that they may proceed.

In some implementations, the secured multi-channel authentication methodallows a single user to upgrade his/her authentication level viamultiple channels whereby the user is able to access a resource whereinaccess to the resource requires a second authentication parameter. Insome implementations an additional authentication parameter is requiredover a second or additional channel. The second or additionalauthentication parameter can be provided from a second device associatedwith the user.

In a first implementation of accessing the requested resource a userfollows a traditional authentication process at a website by enteringtheir ID and password on a login page. In other embodiments, the usermay authenticate using a multi-channel authentication process. Afterlogging onto the website, the user navigates the website at an initialresource access level. When the user navigates to, or requests aresource that requires a higher authentication access level they aredirected to a page that presents a token value. The page then directsthe user to user agent 2 102 to provide an additional authenticationparameter. This can be associated with a second channel 6 or anadditional channel 7.

The user chooses a second channel 6 or an additional channel 7 (e.g. thephone) and dials the given number. In other implementations, the usermay access a second channel through a handheld device, cell phone, orother web channel. The user inputs the token value over the secondchannel, and provides the second or additional authentication parameter,such as a hard token, answer to secure question, or voice print. Theauthentication parameter entered on the phone channel is validated. Thetoken value provided serves to link to the session on the first channel(e.g., the web). When the user completes the necessary process the usersession on the first channel 5 is upgraded to the higher authenticationaccess level.

In some implementations because the user provided authenticationparameters securely and independently via two or more separate channels(e.g. web and phone), the user may be authenticated on all channels andmay proceed on any of these authenticated channels. Therefore, thephone, or second channel 6, associated with user agent 2 102, can havethe same level of authentication as the web, or first channel 5,associated with user agent 1 101.

FIG. 3A shows a user requesting (50) access to a low level resource. Theresource redirects (51) the unauthenticated user to a traditionalauthentication. The user is challenged (12) by the AuthenticationService (AS) 202 to provide (54) their user ID and password. The AS 202forwards (55) the user ID, the PIN and the context to the authenticationvalidator 204 which authenticates (35) the user identity and password.Then, the AS 202 requests the ID System 206 to map (16) the user ID intotheir global ID (17). The AS 202 creates (59) a low value resourceauthentication credential that the AS 202 returns (60) to the user agent1 101. The user now has full access to the low value resource 303.

Later in the session when the user requests (63) a higher value resource307, they will need stronger authentication credentials (64) to accessthis resource. The user is redirected (65) by the AS 202 to acquirestronger authentication credentials. After the user indicates (66) adesire for the stronger authentication credential, the AS 202 acquires(33) the user ID and requests to the session DB 208 to create (18) arecord that includes: user ID, global ID, authentication context(including channel) and session ID. The session DB 208 creates (19) atoken value, and combines the token value with the other values providedand the current time. In some embodiments, the session database 208 alsocreates (19) a session database entry, setting its authentication statusvalue to in-progress. The session DB 208 returns (20) all of thisinformation to the AS 202, which uses the data to update (71) thecurrent user authentication credential with the token value and thetime. The AS 202 sets (22) the authentication credentials on user agent1 101 and presents the token value to the user with instructions tocomplete the additional authentication steps on another channel.

Methods in FIGS. 3B1 and 3B2 are similar to FIGS. 2B1 and 2B2. Thesecond authentication parameter used to fulfill this higher levelresource access requirement may be a password in some implementations.In other implementations, the second authentication parameter may be anyappropriate second factor including a wireless applet, a voice print, aphone-only PW, a soft token, or a hard token. In an alternativeimplementation, FIG. 3B3, the user may use a phone channel as the secondchannel and a voice print as the authentication parameter. In thisimplementation, the AS 202 sends (132) a request for a voice phrase tothe voice authentication validator 303. The voice authenticationvalidator 303 sends (133) a Voice Phrase XXX to the AS 202, which thenrequests (134) that the user say XXX. The user then responds by sayingXXX 135, the designated voice phrase XXX is then forwarded to the voiceauthentication validator 303 which authenticates (136) the user ID, theuser voice for phrase XXX and the context. The voice authenticationvalidator 303 then sends (35) notice to the AS 202 that theauthentication was successful. The AS 202 forwards (36) an updatedauthentication status to the session database 208, which sets (82) theauthentication status as authentication upgrade. An updated statusmessage is then sent (38) to the AS 202, and the AS 202 requests (39)that the user continue their session on user agent 1 101.

Alternatively, the user may continue their user session on either thefirst or second channel and the authentication strength is deemed thesame on both channels once the user completes the authenticationprocedure. In FIGS. 3B4-3B6, the AS 202 creates (88) an authenticationcredential to use on the second channel. The AS 202 may then request(39) that the user continue his session on user agent 1 101, but theuser can also continue (90) his session on user agent 2 202.

In FIG. 3C1, after the user has completed the authentication steps onthe second channel (i.e. user agent 2 102), they return to the firstchannel and request (98) authentication upgrade completion. The AS 202requests (30) the session database record associated with the tokenvalue provided. The session DB 208 returns (31) the session databaserecord that can include, for example, the user ID, global ID,authentication context, token value, session ID, creation time andauthentication status. The authentication service 202 validates 91 thetime, authentication status and global ID and sends indication (43) tothe session DB 208 which updates (44) the authentication status in thesession database 208 to authentication upgrade complete. The session DB208 then transmits (45) the updated status back to the AS 202. Now, theupgraded authentication credentials are built (94) and returned (95) touser agent 1 101. The user is redirected (96) back to access the higherlevel resource that was requested. In another implementation (e.g., FIG.3C2) the user completes the authentication process on either the firstor second channel. In FIG. 3C2, the user requests (99) the channelauthentication upgrade for the high-level resource on both the first andthe second channel. After the credential is established for bothchannels, the user can continue to complete the authentication processas depicted in FIG. 3C1.

The process of requiring higher level access authentication credentials,as higher-value resources are requested, can be repeated for as manytypes of high-level access resources as are needed. Further, additionalfactor authentication for higher level resource access can be requiredat initial login and not delayed until the higher level resource isactually requested.

Some implementations may also incorporate device registration. Deviceregistration allows an authenticated user to register a specific deviceas secure for high level resource access, whereby the user is notrequired to provide an additional or second authentication parameterwhen the user requests access to the high-level resource in the future.

In FIGS. 4A1 and 4A2, the user follows the same process as described inFIG. 3A. However, after the ID System 206 returns the global ID 17, theAS 202 requests (142) the strong authentication method for the user IDand the ID system 206 returns (143) the secure device registration. TheAS 202 can determine if the user is registered for a secure devicecredential 144, if the secure device credential exists 145, and if thedevice security credential user ID match the current user ID entered bythe current user 146.

FIG. 4A1 shows one implementation where the secure device credentialdoes not exist. In FIG. 4A1, after the AS 202 determines that the securedevice credential does not exist 145, the AS 202 creates a (59)low-level resource credential, and provides (60) the authenticationcredential for the lower-level resource to the user. The user thenfollows the same process of FIG. 3A to request and access a resourcethat requires a second or additional authentication parameter. Inaddition, in some implementations, the AS 202 may include (70) a securedevice registration along with the authentication credential thatincludes the token value and time.

In FIG. 4A2, a secure device credential exists but does not match thecurrent user ID 146. In this implementation, the AS 202 creates (59) theauthentication credential for the initial authentication level, andprovides (60) the authentication credential while deleting the devicesecurity credential. The user then follows the same process of FIG. 4A1to request a resource that requires a second or additionalauthentication parameter.

In FIG. 4A3, the secure device credential exists and matches the currentuser ID 146. In this implementation, the AS 202 creates a high-valueauthentication credential 68 for a resource that requires an additional,or second authentication parameter. The AS 202 then provides the highlevel authentication credential to user agent 1 101. The user is nowable to access the resource that requires an additional, or second,authentication parameter without having to provide the additional, orsecond authentication parameter over the second channel.

The implementations disclosed in FIGS. 4B1-4B3 are similar to thosedisclosed in FIGS. 3B1-3B3 except that in the implementations shown inFIGS. 4B1-4B3 after the authentication validator 204 indicates (35) tothe AS 202 that the authentication is successful, the AS 202 determines(137) if secure device registration is needed. If secure deviceregistration is desired, the AS 202 sends a request to user agent 2 102asking (138) if the user wants to register the device associated withuser agent 1 101 as a long-term secure device. The user may thenindicate (139) that they do want to register the device. The sessiondatabase 208 sets (141) the authentication status to authenticationupgrade and the secure device registration to long term. The updatedstatus is returned (38) to the AS 202 which requests (39) that the usercontinue their session on user agent 1 101. In some implementations thefirst device, or the device associate with user agent 1 101, may beregistered as a permanently long-term secure device. In someimplementations, the device may be registered for the current session,in some implementations the device may be registered for a limitedamount of time or specified number of user sessions, long-ins, orrequests for the resource. In FIG. 4B1 the user may be asked if securedevice registration is needed when the phone can be the secondchannel/device, in FIG. 4B2 a wireless/cell phone applet can be thesecond channel/device, and in FIG. 4B3 the phone can be the secondchannel/device and the user's voice can be the authentication parameter.

In FIG. 4C, when control is returned to the first device over the firstchannel, the AS 202, upon seeing the device registration in the sessiondata, generates (169) a persistent credential that specifies the ownerand the type of credential that has been enabled for the first device.The AS 202 also upgrades (94) the authentication credentials, notice(171) of the updated authentication and secure device credential arethen returned to user agent 1 101. Subsequently, when the user requests(96) a high-value resource over user agent 1 101, the resource requestis successful 97.

On subsequent upgrade authentication requests to the AS 202, thecredential, which may be a persistent cookie in some implementations, isfound and examined. And if the user and the device are registered forsecure access to the requested resource(s), then the upgrade iscompleted without recourse to the second, or additional, channel (e.g.FIG. 4A3).

FIGS. 5A1-5C comprise different but related implementations thatdescribe how an authenticated, or second user may provide an indicationof approval for a third-party, or first user, to be authenticated andact as the registered user. In some implementations, the first user willonly have access to the second user's account, and in someimplementations the first user will have access to a resource thatrequires the indication of approval. The third-party is able to accessat least some of the registered user's resources without the registereduser exposing their private authenticating information to thethird-party user. In some implementations, the first user who desiresaccess to the account or resource is not known by the resource providerand in some implementations the first user may not have an account withthe resource provider. In some implementations the first user isassociated with user agent 1 101 and a single registered user will beassociated with user agent 2 102. In some implementations, the processassociated with user agent 2 102 may be carried out by N differentregistered/authenticated users, all who provide an indication ofapproval for the first user to be authenticated or to have access to therequested resource.

In FIG. 5A1, a first user requests access to the account of a registereduser. FIG. 5A1 is identical to FIG. 2A above. However, in FIG. 5A1 thesecond user, here the account-owner/registered user, gives a firstauthentication parameter, which may include a user ID in one embodiment,to the interested third-party/first user. The first authenticationparameter provided to the first user can also be, for example, adescriptive title, identifying number, or SSN. The third-party userenters (13) the user ID on the first channel. The AS sets (22) theauthentication credential on user agent 1, and the first user ispresented with a token value and instructed to complete authenticationon another device/channel. The first user can communicate the tokenvalue to the second user, or registered user, associated with user agent2 102.

In FIG. 5B1 the second user associated with user agent 2 102 accessesthe system via a second, channel, or, in an alternative implementation,a different device on the same channel. In some implementations, thesecond user enters (27) the token value and the second authenticationparameter (29), which in one embodiment can be a password or PIN.Alternative or additional embodiments of the second authenticationparameter may be a user ID, a descriptive title, password, hard token,soft token, wireless applet, voiceprint, or any combination thereof.Subsequently, the second user can follow the process depicted in FIG.2B1.

Some implementations further protect the registered user's identity. InFIG. 5A2, the interested third-party, or first user, accesses (120) awebpage 121 where they enter (122) personal descriptive information,like their name or their function. Examples of the personallydescriptive information may include financial advisor, broker, doctor,tax preparer, or spouse in some embodiments. In some implementations,the requested resources may be the authentication of the first user, insome implementations the resource is information that is restricted orrequires the approval of the second user, and in some implementationsthe resource may be access to the registered or second user's personalaccount or information, or authorization to complete a transaction. InFIG. 5A2, the AS 202 creates a record 18 that includes the user info,access context, and channel information. The session database 208creates (19) a token value, sets the current time, and setauthentication status to in-process. After the session database 208returns (20) the token value and time to the AS 202, the AS creates(124) an authentication credential reflecting that the user is notauthenticated, the token value, and the time. The first user ispresented (72) with a token value that they communicate to theregistered user.

After receiving the token value and the request to complete theauthorization process on a second channel, the registered or second userauthenticates themselves in some implementations. The second user mayauthentication themselves through a traditional authentication process,in other implementations the second user may authenticate themselvesuses the multi-channel process shown in FIGS. 2A-2C. Next, the seconduser may access an alternate, or second channel that challenges (26)them for the token value. In FIG. 5B2, after the AS 202 validates thetoken, authentication, context, time and status 251, the second user ispresented (251) with the descriptive information that was entered by thethird-party. If satisfied, the second user can authorize (252) thethird-party user's access. Upon receiving the indication ofauthorization from the second user, the AS 202 updates the authorizationstatus and the session DB 208 updates (255) the session record,including setting the authorization 36 status to authorized. The updatedstatus is returned (38) to the AS 202, and the AS requests (154) thatthe second user inform the first user that the first user may continuethe session on user agent 1 101. As before, in FIG. 5C, the third-partyuser continues on the first channel and is granted an authenticationcredential as if they were the registered user.

In FIGS. 5A2 and 5B2, none of the second (registered) user'sauthentication information was exposed to the third-party because thesecond user is allowed to withhold the password or authenticationparameter from the first user and enter their authenticationparameter(s) over a second channel. The second user's user ID, or otherfirst authentication parameter in alternative embodiments, may beexposed but not the second user's Password, or second authenticationparameter. In some implementation the second user ensures that theiraccount is safe from unauthorized access by the first user at a latertime and that none of their authentication information is publiclydistributed. However, the authorization context may permit the firstuser access to the second user's personal information, financial, orother sensitive materials and information. The first user is thereforeable to access the second user, or registered user's account informationwith limited exposure of the second user's authentication parameters.

In FIG. 5C, after the second user enters the second authenticationparameter on the second device (associated with user agent 2 102), thefirst user continues on the first channel associated with user agent 1101 (see e.g., FIG. 2C), and is granted an authentication credential asif they were the owner of the account.

In FIG. 6, a registered user accesses a third-party session that wasauthorized or authenticated by the registered user and can terminate thesession if desired. In other implementations, the second (registered)user may upgrade or downgrade the access of the first user to theresource or multiple resources. In some implementations, the registereduser who is associated with user agent 2 102, requests to be connected(25) to a resource that determines the status of a session associatedwith the first user. The system then requests the token value (26) andthe authentication parameter which may be a channel specific PIN (29)associated with the user. After the registered user enters the tokenvalue and their Password, the back-end system updates (36) theauthentication status of the user session associated with the first userto reflect the status indicated by the second user 126. In someimplementations, the status may be session terminated, in otherimplementation it may be session downgrade or upgrade. The second useris notified (128) that the first user's session has been terminated. Insome implementations, the second user will be notified that the firstuser's access has been upgraded or downgraded. The status is kept withthe session data (127) associated with the third-party user's sessionID. When the third party user next requests (129) the resource, thetermination status 130 is detected and the third-party user session isended (131). In some implementations, an upgraded or downgraded statusof the first user's session may be detected and the first user's sessionis appropriately modified to reflect the new status set by the seconduser (account owner/registered user).

In similar and related implementations, FIGS. 7A1-7C1 and FIGS. 7A2-7C2show how to provide a means for a parent to authorize session-wide andtransaction specific access to requested resources by an otherwiseaccess-restricted, minor-child account holder. FIG. 7A3 also describes ameans to provide a joint account type authorization facility forresources that require multiple user approval.

In one implementation a first user authenticates themselves, but stillrequires an authenticated second user to authorize the first user'ssession. In FIG. 7A1, the first user, here a minor child, has an accountand is logged-in and navigating to low level resources. Theimplementation shown in FIG. 7A1 is similar to the implementation shownin FIG. 3A. However, in FIG. 7A1 when the child requests (63) a resource307 that requires a stronger authentication parameter (e.g. parentalapproval), the high-value resource validator 305 indicates (87) thatparental approval is necessary. In some implementations the resource canbe a change of personal data, in other implementations the resource canbe a limited-access website, or in an other implementations the resourcecan be a requested transaction. The high-value resource validator 305redirects (65) the first user to complete the process necessary toaccess the restricted resource. The minor is presented (72) a tokenvalue and the instruction to communicate the token value to the seconduser, their parent, and have their parent allow access to the minor.

In another implementation a first user will authenticate themselves, butstill requires that a second user authorize the first user's access to arequested resource. FIG. 7A2 shows one implementation where a firstuser, here a minor, tries to complete a transaction but the minor doesnot have the authentication credentials required by the resource. Insome implementations, the minor can access lower-level resources withoutthe higher value credential(s). When the minor requests (63) a higherlevel resource 307 that requires parental approval, the AS 202recognizes (87) that the first user's request requires parental approvalto complete. In some implementations this approval may be provided byany second user who is authorized to approve the first user's requestfor the resource, for example a teacher or supervisor. The AS 202directs (67) the session database 208 to create a transaction recordthat includes the user ID, global ID, transaction details, channel,parental approval and session ID. The session database 208 sets (56) theauthentication status by deleting the transaction ID records for theuser ID 1, session ID 1 and sets the authentication status as open, orin an alternative implementation as user 1 (first user) approved. Thesession database 208 also creates (57) a transaction ID value, and setsthe current time and authentication status as open. The minor isredirected (65) to the AS 202 to acquire stronger authenticationcredentials, in this implementation: parental approval. The AS 202acquires (33) the user ID and makes a request (18) to the Session DB 208to create (31) a record that includes, for example, user ID, global ID,transaction details, channel, parental approval and session ID. Thesession DB 208 retrieves the last transaction ID for user ID1, and thesession ID 58, creates (69) a token value, combines the token value withthe other values provided and the current time. The session database 208also can create a session database entry, setting its authenticationstatus value to in-progress, or in some implementations to in-progress,transaction ID. The session DB 208 returns (20) this information to theAS 202 which uses this information to update (71) the current userauthentication credential with the token value and the time. The AS 202sets authentication credentials on user agent 1 101 and presents (72)the token value to user agent 1 101, with instructions to inform aparent to complete the additional authentication steps on anotherchannel, which may be, for example, user agent 2 102. In someimplementations, the first user is instructed (72) to inform the otherjoint account owner to authorize the transaction on anotherdevice/channel (e.g., FIG. 7A3).

After completing the process disclosed in FIG. 7A1 or 7A2, the minorcommunicates the token value to a parent and asks the parent to indicateapproval for the minor's access to the resource. In some implementation,FIG. 7B1, the parent authenticates themselves. In some embodiments, theparent, or second user, may authenticate themselves using a traditionalsingle channel method, while in other embodiments, the parent/seconduser may authenticate themselves using a multi-channel method, which insome implementations may be similar to the method disclosed in FIG.2A-2C above. In this embodiment, the parent, associated with user agent2 102, requests parental authorization 78.

In FIG. 7B1, the parent may use the phone as the second channel. In someimplementations, the parent, or second user, may use a computer, or awireless device like a cell phone, a handheld computing device, a PDA,or a Blackberry device. The Authentication Service 202 requests (30) thesession data from the session DB 208, based on the inputted token value.The session DB 208 uses the token value to acquire and return (31) thedatabase record including, for example, the entry creation time, userID, global ID, authentication context, token value, session ID, time,channel, parental approval for the session, and the authenticationstatus to the AS 202. In some implementations the session DB 208 canreturn instructions requiring parental approval of the session (174).The AS 202 validates (80) the token and time. The ID system 206 confirms(147, 148) that the second user is an “authorized parent” for the firstuser. If the second user is an authorized parent, the AS 202 presents(149) the first user's information to user agent 1 101 and requests thatthe second user approve the first user's to access the requestedresource. After verifying the first user's information, the parentauthorizes (150) the request, and the AS 202 updates (36) theauthorization status. The session DB 208 updates the authorizationstatus with the parent authorization upgrade and the parentauthentication information 152, and notifies (38) the AS 202 that thestatus has been updated. The AS 202 requests that the session becompleted (22) on the first channel associated with user agent 1 101. Insome implementations, the AS request (154) that the second user informthe first user to continue their session on the first channel.

In FIG. 7B2, after the ID system 206 confirms (147, 148) that the seconduser is an “authorized parent” for the first user, the AS 202 requestspermission to proceed with the transaction (177). After the second usergrants permission to proceed 178, the AS 202 requests (179) thetransaction database record (Transaction ID) from the session database208. The session database 208 provides the transaction details 180through the AS 202, which passes (181) the transaction details to thesecond user and asks for the second user to approve the transaction.After verifying the transaction detail information, the second userindicates their approval (150), and the AS 202 updates (36) theauthorization status. The session DB 208 sets the authorization statusto parent authorization upgrade for transaction and parentauthentication information 185. In addition, the status of the sessionis marked as parental approval and the transaction record reflects thetransaction ID, and an appendix to the record with the second user'sauthentication information is created. An updated status message is sent(38) to the AS 202, and the AS 202 requests (154) that the second userinform the first user that they may continue their session on user agent1 101.

In FIG. 7C1, after the second user (Parent) has authenticated orauthorized the first user's (minor's) request for the resource, thefirst user may continue his session (155) on the first channel/device.The AS 202 obtains the token value, the global ID, and the time from theauthentication credential delivered with this user request. Using thetoken value, the AS 202 requests (30) the session DB 208 to acquire thesession database record associated with the token value provided. Thesession DB 208 returns (31) the session database record that includesthe user ID, global ID, authentication context, token value, session ID,creation time, channel, and authentication status in someimplementations. The authentication service 202 validates (91) the time,authentication status and global ID and confirms, in someimplementations, that there is parental approval 159 for the session. Inother implementations other forms of approval may be validated. The AS202 uses the session DB 208 to update (43) the authentication status inthe session database to parent authorization upgrade complete (161). Insome implementations the authentication status may be updated to reflectthat joint approval is complete. The AS 202 now reflects the upgradedauthentication credentials, which in some implementations may reflectparental approval, and in some implementations (FIG. 7C2) may reflect nostrength upgrade 187.

In FIG. 7C1, the upgraded authentication credentials, including anindication of parental approval in some embodiments, are built (163) andreturned (95) to user agent 1 101 and the first user is redirected (96)back to access (97) the higher level requested resource.

In some implementations, FIG. 7C2 would follow after FIG. 7B2. After theAS 202 creates the updated authentication credential 187, which in thisimplementation contains no strength upgrade, the updated authenticationcredential and the transaction ID are returned (188) to the first user.The first user requests (189) the high-value resource and provides thetransaction ID, which is used to retrieve (190) the transaction record.The session database 208 returns (191) the transaction record, which isvalidated (192) for parental approval, or another form of approval insome implementations, and the transaction details are posted (193). Theresource validator 306 then updates (194) the transaction record withthe session database 208, which records the status as transactioncomplete 195. The first user 101 is informed that the transaction wascompleted (97). The transaction is completed because the second user102, or parent's, electronic signature authorizing the transaction, aswell as the transaction details were captured during the authorizationprocess, allowing the transaction to be executed.

In FIG. 7A3, a holder of a joint account attempts to perform atransaction that requires the approval of both account participants. Thetransaction application creates and sets an electronic signature requestrecord into a session database 208 then it redirects the user to theauthentication service 202. In some implementations the record willinclude user ID, global ID, transaction details, channel, joint approvalfor transaction, and session ID. The authentication service 202 createsa joint user session database entry that refers to the signature requestentry. The entry may contain a session ID and sign status with anindication that the first user is approved. The token value created forthis entry is returned to the first account holder with instructions forthe second account holder to complete the approval process.

The second account holder, associated with user agent 2 102, logs on tothe system and navigates to a location where they are asked for thetoken values. The electronic signature request is presented along with adisplay of the details of the transaction being requested (e.g., FIG.7B3). The second user approves the transaction and informs the firstuser that the first user may complete the transaction 154.

In FIG. 7C3, the first user continues in an implementation similar tothe FIG. 7C2. However, in this implementation, the AS 202 searches forjoint approval 329 for the transaction, and the transaction record is anelectronic signature record 335 and the resource requested is jointauthorization for a transaction secured by the electronic signature.This causes the electronic signature transaction to be extracted fromthe session database 208 and presented to the application for execution.The user is informed of the completion of the requested transaction.

Another implementation of the multi-channel method includes a requestedcredit card transaction. In a first implementations, the user requeststhat credit card issuer contact user via a specific device for alltransactions over a certain dollar amount. When the card is swiped andthe transaction amount input for authorization exceeds user-definedlimit, the user is contacted over the selected device by the credit cardissuer back-end system and asked to provide an ID and credential, orother authentication parameter. This request for the authenticationparameter may be executed at the time of purchase, or point of sale insome implementations, in other implementations the credit card back-endsystem may contact the credit card account owner, at another time thatis not the time of sale. The back-end system authorizes the transactiononly after the credentials are validated.

In another implementation, a credit card transaction may be authorizedor authenticated using multiple channels. In a first implementation thisincludes, for example, a credit card service 401, credit cardauthorization 402, an AS 202, an authentication validator 204, an IDsystem 206, and a session database 208.

In FIG. 8A, a merchant associated with user agent 1 101 tries to make atransaction using a credit card on behalf of a credit card owner. Inthis embodiment the Credit card service requests validation (410) forthe transaction, when the transaction is more than thepreviously-determined allowed limit 412. The credit card authorization402 forwards the authorization process to the AS 202, authenticationvalidator 204, ID system 206 and session DB 208, which create a record,and creates a session 422 with the token value and time. The user isprovided with a prompt 424 to call and authorize the transaction.

In FIG. 8A, the first user, which may be for example the credit cardreader at the point of sale, sends a request (410) to the credit cardauthorization 402. The credit card authorization 402 determines if theamount is greater than the predetermined limit 412. If the amountrequested for the transaction is greater than the pre-determined limit,then the credit card authorization 402 retrieves the user ID 413 and theglobal ID 16, and map the credit card number to the global id and userID for the ID system 206. The ID system 206 returns the global ID andthe user ID 58′ to the AS 202 which then creates a transaction record414. The transaction record included user ID1, global ID1, thetransaction details, the credit card processor ID, channel 1, and thecredit card approval for the transaction. Next, the session DB 208 setsthe authentication status 415 by deleting the credit card transaction IDrecords for user ID1, and setting the credit card processor ID andauthorization status to credit card open. Next, the credit cardauthorization 402 requests the AS to create (418) a record that includesthe credit card number, the credit card transaction ID, the global IDand the user ID 418. After creating the record 419, the session Dbcreates a token value and sets the authentication status to: In Process412. The session DB 208 then returns the token value and the time (70)to the credit card authorization 402 which creates a session associatedwith the token value 422 and prompts the credit card service, whichsubsequently prompts the user (423, 424) to authorize the transactionassociated with the token value on a second channel. In someimplementations, the credit card reader may use a phone or telephoneline as a second channel. In some implementations, the credit cardowner, or second user who is associated with user agent 2 may use acomputer or wireless device to authorize the transaction.

In some implementations, the call to authenticate or authorize thetransaction may be initiated by the credit card company. In someimplementations, the credit card company will have phone numbers onrecord to call a second user when a transaction is made that requiresadditional authentication or authorization.

In FIG. 8B, the merchant passes the token to the credit card owner andrequests that they complete the authorization process. In someimplementations the credit card owner, or second user may authenticatehimself through a traditional authentication process on an additionalchannel, in other implementations the second user may authenticatehimself using a multi-channel process which in some embodiments may besimilar to the process shown in FIGS. 3A-3C1. In some implementationsthe second user, or credit card owner, may authenticate themselves onthe second channel associated with user agent 2 102. The second user mayauthenticate themselves on the channel associated with user agent 2 102by entering the token and a user ID and password in someimplementations, or a second and/or additional authentications parameterin an alternative implementation. The second user, who is now associatedwith the second channel now follows a process similar to the processdisclosed in FIG. 7B2. In this implementations parental approval is notrequired, but rather the second user must be authorized to make thecredit card transaction (427) and approval for the credit cardtransaction is needed. The authorization and approval are both stored bythe back end system in the credit card transaction record 432. After thesecond user provides approval for the transaction (434), the status ofthe session associated with requested credit card transaction is updated(86). The second user is then instructed (154) to inform the first user,or merchant, to complete the transaction.

In 8C, the second user completes the transaction if the authenticationparameters entered by the second user, or credit card account owner arevalidated. In some implementations, the second users can indicateapproval for the transaction to proceed. The credit card authorization402 provides the approval, token value, and credit card number to the AS202 which requests (30) the database record. The session DB 208 returns(31) the database record that includes the user ID, global ID,authentication context, token value, session ID, time, channel, creditcard transaction approval, and status. The AS 202 then validates thesession DB record, and determines (39) that the credit card ownerprovided approval for the transaction. The updated authentication status36 is then returned to the session DB 208, which sets (440) theauthentication status to credit card transaction approval complete. Theupdated status is then returned (38) to the AS 202, and the approvedcredit card transaction ID 441 is retuned to the credit cardauthorization 402. The credit card authorization validates (444) thecredit card account owner's approval and posts (445) the transactiondetails. The credit card authorization 402 then updates (446) the creditcard transaction record in the session DB 208, which records the newstatus as credit card transaction complete 447. After the status isupdated, the credit card authorization sends notification (401) of thecompleted transaction and the receipt to the credit card service 401which then forwards (449) the information onto the end-user associatedwith user agent 1 101.

The above-described techniques can be implemented in digital electroniccircuitry, or in computer hardware, firmware, software, or incombinations of them. The implementation can be as a computer programproduct, e.g., a computer program tangibly embodied in an informationcarrier, e.g., in a machine-readable storage device or in a propagatedsignal, for execution by, or to control the operation of, dataprocessing apparatus, e.g., a programmable processor, a computer, ormultiple computers. A computer program can be written in any form ofprogramming language, including compiled or interpreted languages, andit can be deployed in any form, including as a stand-alone program or asa module, component, subroutine, or other unit suitable for use in acomputing environment. A computer program can be deployed to be executedon one computer or on multiple computers at one site or distributedacross multiple sites and interconnected by a communication network.

Method steps can be performed by one or more programmable processorsexecuting a computer program to perform functions of the invention byoperating on input data and generating output. Method steps can also beperformed by, and apparatus can be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit). Modules can refer to portionsof the computer program and/or the processor/special circuitry thatimplements that functionality.

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor receives instructions and data from a read-only memory or arandom access memory or both. The essential elements of a computer are aprocessor for executing instructions and one or more memory devices forstoring instructions and data. Generally, a computer will also include,or be operatively coupled to receive data from or transfer data to, orboth, one or more mass storage devices for storing data, e.g., magnetic,magneto-optical disks, or optical disks. Data transmission andinstructions can also occur over a communications network. Informationcarriers suitable for embodying computer program instructions and datainclude all forms of non-volatile memory, including by way of examplesemiconductor memory devices, e.g., EPROM, EEPROM, and flash memorydevices; magnetic disks, e.g., internal hard disks or removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor andthe memory can be supplemented by, or incorporated in special purposelogic circuitry.

The terms “module” and “function,” as used herein, mean, but are notlimited to, a software or hardware component which performs certaintasks. A module may advantageously be configured to reside onaddressable storage medium and configured to execute on one or moreprocessors. A module may be fully or partially implemented with ageneral purpose integrated circuit (“IC”), FPGA, or ASIC. Thus, a modulemay include, by way of example, components, such as software components,object-oriented software components, class components and taskcomponents, processes, functions, attributes, procedures, subroutines,segments of program code, drivers, firmware, microcode, circuitry, data,databases, data structures, tables, arrays, and variables. Thefunctionality provided for in the components and modules may be combinedinto fewer components and modules or further separated into additionalcomponents and modules. Additionally, the components and modules mayadvantageously be implemented on many different platforms, includingcomputers, computer servers, data communications infrastructureequipment such as application-enabled switches or routers, ortelecommunications infrastructure equipment, such as public or privatetelephone switches or private branch exchanges (“PBX”). In any of thesecases, implementation may be achieved either by writing applicationsthat are native to the chosen platform, or by interfacing the platformto one or more external application engines.

To provide for interaction with a user, the above described techniquescan be implemented on a computer having a display device, e.g., a CRT(cathode ray tube) or LCD (liquid crystal display) monitor, fordisplaying information to the user and a keyboard and a pointing device,e.g., a mouse or a trackball, by which the user can provide input to thecomputer (e.g., interact with a user interface element). Other kinds ofdevices can be used to provide for interaction with a user as well; forexample, feedback provided to the user can be any form of sensoryfeedback, e.g., visual feedback, auditory feedback, or tactile feedback;and input from the user can be received in any form, including acoustic,speech, or tactile input.

The above described techniques can be implemented in a distributedcomputing system that includes a back-end component, e.g., as a dataserver, and/or a middleware component, e.g., an application server,and/or a front-end component, e.g., a client computer having a graphicaluser interface and/or a Web browser through which a user can interactwith an example implementation, or any combination of such back-end,middleware, or front-end components. The components of the system can beinterconnected by any form or medium of digital data communications,e.g., a communications network. Examples of communications networks,also referred to as communications channels include a local area network(“LAN”) and a wide area network (“WAN”), e.g., the Internet, and includeboth wired and wireless networks. Unless clearly indicated otherwise,communications networks can also include all or a portion of the PSTN,for example, a portion owned by a specific carrier.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communications network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

The invention has been described in terms of particular embodiments. Thealternatives described herein are examples for illustration only and notto limit the alternatives in any way. The steps of the invention can beperformed in a different order and still achieve desirable results.Other embodiments are within the scope of the following claims.

1. A method for using multiple channels to authenticate a user, themethod comprising: receiving a first authentication parameter from afirst device associated with a user over a first channel, wherein theuser is unauthenticated; transmitting a token value; receiving the tokenvalue and a second authentication parameter from a second device over asecond channel, wherein the second device is associated with the user;and using the token value to associate the first authenticationparameter to the second authentication parameter.
 2. The method of claim1, further comprising: authenticating the user based on the firstauthentication parameter and the second authentication parameter.
 3. Themethod of claim 1, further comprising: notifying the user over thesecond channel that the authentication is complete.
 4. The method ofclaim 1, further comprising: allowing the user to continue a usersession on the first channel.
 5. The method of claim 1 wherein the firstchannel is a phone line, a wireless connection or an online connection.6. The method of claim 1 wherein the second channel is a phone line, awireless connection, or an online connection.
 7. The method of claim 1wherein the first authentication parameter is a user ID, password, hardtoken, soft token, wireless applet, voiceprint, or any combinationthereof.
 8. The method of claim 1, wherein the second authenticationparameter is a user ID, a password, a hard token, a soft token, awireless applet, a voiceprint, or any combination thereof.
 9. The methodof claim 1, wherein the first authentication parameter and the secondauthentication parameter are channel specific.
 10. The method of claim1, further comprising: receiving the token value and at least oneadditional authentication parameter over at least one additionalchannel.
 11. The method of claim 10, wherein the additionalauthentication parameter is a user ID, a password, a partial password, aportion of the first authentication parameter, a portion of the secondauthentication parameter, or a combination of the first and the secondauthentication parameters, a hard token, a soft token, a wirelessapplet, a voiceprint, or any combination thereof.
 12. The method ofclaim 10, further comprising using the token value to associate thefirst authentication parameter, the second authentication parameter, andthe at least one additional authentication parameter.
 13. The method ofclaim 10, further comprising using the first authentication parameter,the second authentication parameter, and the at least one additionalauthentication parameter to authenticate the user.
 14. The method ofclaim 10, wherein the at least one additional channel is not the firstor second channel.